Skip to content

fix(pricing): drop "small/medium deployment" size adjectives from dashboard + landing tiles#143

Merged
mastermanas805 merged 1 commit into
mainfrom
fix/dashboard-pricing-copy
May 29, 2026
Merged

fix(pricing): drop "small/medium deployment" size adjectives from dashboard + landing tiles#143
mastermanas805 merged 1 commit into
mainfrom
fix/dashboard-pricing-copy

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

Summary

BIZ-3 from the QA backlog (P1). Two pricing surfaces — the dashboard in-app PricingGrid and the landing-page pricing tile in MarketingPage — shipped copy inherited from a retired deployment_size field on POST /deploy/new.

  • Hobby tile: "1 small deployment"
  • Pro tile: "50 GB object storage · 10 medium deployments"

The API handler (api/internal/handlers/deploy.go) has no deployment_size field. There are no small / medium / large pod sizes. Numbers come from plans.yaml deployments_apps. Marketing /pricing (PricingPage.tsx) dropped the size adjectives in the 2026-05-20 DOC-REALITY-DELTA sweep; the dashboard PricingGrid and the landing MarketingPage tile lagged.

What changed

  • src/components/PricingGrid.tsx — Hobby: 1 deployment. Pro: 50 GB object storage · 10 deployments.
  • src/pages/MarketingPage.tsx — same copy on the landing tile.

Regression coverage

  • src/components/PricingGrid.test.tsx (new) — 4 assertions:
    • no small deployment substring rendered
    • no medium deployments substring rendered
    • Hobby tile renders 1 deployment
    • Pro tile renders 10 deployments
  • src/pages/MarketingPage.test.tsx — adds the two negative assertions on the landing tile suite.

Gate

npm run gate green locally — 1044 passed | 3 skipped (75 test files).

Live verify (after merge)

curl -s https://instanode.dev/pricing | grep -c "small deployment"     # expect 0
curl -s https://instanode.dev | grep -c "medium deployments"           # expect 0

Surface checklist (rule 22)

Contract-aligned pricing copy already in plans.yaml + common/plans + OpenAPI + content/llms.txt + marketing PricingPage.tsx. This PR brings the in-app PricingGrid and the landing tile in line with the rest.

🤖 Generated with Claude Code

…hboard + landing tiles

BIZ-3 (QA backlog, P1). The dashboard in-app PricingGrid and the landing
pricing tile both shipped copy inherited from a retired deployment_size
field on POST /deploy/new:

  - Hobby tile: "1 small deployment"
  - Pro tile:   "50 GB object storage · 10 medium deployments"

The API handler (api/internal/handlers/deploy.go) has no deployment_size
field — there are no small / medium / large pod sizes. Numbers come from
plans.yaml deployments_apps. Marketing /pricing (PricingPage.tsx) dropped
the size adjectives in the 2026-05-20 DOC-REALITY-DELTA sweep; the
dashboard PricingGrid and the landing MarketingPage tile lagged.

This PR matches the voice that marketing /pricing already ships:
  - Hobby: "1 deployment"
  - Pro:   "50 GB object storage · 10 deployments"

Regression coverage:
  - PricingGrid.test.tsx: 4 assertions pinning the new copy and pinning
    both retired strings out of the rendered DOM.
  - MarketingPage.test.tsx: adds the same negative assertions to the
    landing-tile suite.

Surface checklist (CLAUDE.md rule 22): contract-aligned pricing copy
already in plans.yaml + common/plans + openapi + content/llms.txt + the
marketing PricingPage; this PR brings the dashboard PricingGrid and the
landing MarketingPage tile in line with the rest.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

size-limit report 📦

Path Size
dist/assets/index-DWNtyvwM.js 0 B (-100% 🔽)
dist/assets/index-BsJUZYRr.css 6.13 KB (0%)
dist/assets/index-Ex6CmsJ1.js 163.55 KB (+100% 🔺)

@mastermanas805 mastermanas805 merged commit eb25c04 into main May 29, 2026
16 checks passed
@mastermanas805 mastermanas805 deleted the fix/dashboard-pricing-copy branch May 29, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant